home *** CD-ROM | disk | FTP | other *** search
-
- Changes to opal.library (04-May-93)
-
- IMPORTANT NOTES
-
- You should understand the issues regarding Mode Promotion, horizontal
- synchronisation and Overscan intuition screen positioning as outlined in
- section 11.9 of the developers manual. These issues have caused some
- problems with 3rd party support, so please take a moment to read and
- understand this section.
-
-
- LOADER SAVER INTERFACE (LSI)
-
- A standardised interface for loader and saver programs has been added to
- opal.library, this will be outlined in a seperate document currently being
- prepared. This document should be available in the next week or so.
-
- To give a brief overview, the library maintains a list of active saver and
- loader modules. Each module makes itself available by either calling
- AddOVLoader() or AddOVSaver(), and the current list of modules can be
- determined by calling GetOVSavers() or GetOVLoaders(). Each loader and
- saver if referenced by a unique name. The communication between the
- modules and the library occurs using standard Exec messages.
-
- You will normally not need to be aware of the loader modules. The loading
- sequence will be handled transparently using the LoadImage24() function.
- LoadImage24() initiates a polling sequence which will check all loaders to
- see if they understand the file format, and use the correct loader for the
- image format.
-
- To use the saver modules however (other than IFF,Fast or JPEG), you need to
- use the Export24() function which takes as a parameter the name of the
- saver module. A typical user interface would use the GetOVSavers()
- function to obtain a list of available saver modules for the user to select
- from, once the saver has been selected, the name from the list is simply
- passed to Export24(). Export24() can accept "IFF","Fast" and "JPEG" as
- parameters and use the correct functions to perfrom the save (i.e.
- SaveJPEG24() or SaveIFF24()).
-
-
- Martin Boyd, Opal Technology.
-
-